![]() |
![]() |
![]() |
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
![]() |
![]() |
To access the contents, click the chapter and section titles.
Oracle Performance Tuning and Optimization
Third-Party ToolsMany third-party tools on the market today are excellent. You should take several factors into consideration when shopping for a third-party monitoring tool: Does it fit into your environment? Does it put an undue burden on the system? Does it monitor all the parameters you need? Some products are designed with a particular operating system in mind; some support many different environments; still others monitor only Oracle through SQL*Net and consider the servers operating system irrelevant. Be sure that the monitoring tool you purchase fits into your environment. If possible, get a demonstration version and try it out before you buy. Make sure that the monitoring tool does not put a heavy load on the server. If configured improperly, some products continually extract data from the Oracle internal performance tables, causing undue contention in the system. Try running a benchmark with and without the performance monitor running. Perhaps the collection interval is too fast and can be reduced. It is not necessary to extract performance information from the system every second when a 30-second interval will do. Reducing the collection interval can significantly reduce the load on the system.
Here are some questions you should ask yourself when purchasing a performance monitoring tool. Remember that you will have your own individual needs based on your implementation.
Most third-party tools available today are sufficient for most needs. Be sure to shop around to find the one that is right for you. I have intentionally avoided making any particular recommendations here because there are many good tools on the market todayand they are continually improving. By shopping around, you will find a performance monitoring tool that fits into your existing network and management strategy. Dont judge a tool based on how pretty it looks; look at what it monitors and how it gets its information. The tools available today fall into one of several categories: those that simply monitor parameters and display them on a graphical console, those that alert you when they reach some threshold, and those that are combinations of these first two. The one you need depends on your configuration. Real-Time MonitorsThe real-time monitors usually have a graphical display and provide histograms, or line charts, of various parameters. Real-time monitoring tools are useful for debugging a resource problem or for tuning an application. With these monitors, you can watch the display while you are running to see whether any particular resource is being overused or whether a certain area of the database is experiencing extremely high activity. I recommend a real-time monitoring tool for debugging applications, trying new tuning parameters, or comparing different applications. Because of the type of monitoring being done, these performance monitoring tools typically look at Oracles V$ tables or maybe even the internal X$ tables. Because this can have an adverse affect on the systems performance, use these types of tools periodically to check the health of the system or when you are debugging a problem. Another alternative is to run these tools with a fairly long sample interval (such as 30 seconds or a minute) to reduce the overhead on the system. To monitor the system for a particular problem, consider a threshold monitor. Threshold monitors are used when you dont think you have any problems; they wake up and alert you of some potential or real problem.
|
![]() |
Products | Contact Us | About Us | Privacy | Ad Info | Home
Use of this site is subject to certain Terms & Conditions, Copyright © 1996-2000 EarthWeb Inc. All rights reserved. Reproduction whole or in part in any form or medium without express written permission of EarthWeb is prohibited. |